fix monitor match on gtk bug #34
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nwg-piotr
requested changes
Jul 24, 2024
There was a problem hiding this comment.
This won't work if you have two monitors of the same model. I remember having resolved this in nwg-displays, see: nwg-piotr/nwg-displays@1147265
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix an issue regarding to the monitor matching mechanism. The root cause is the following bug in gtk.
swaywm/sway#8164 https://gitlab.gnome.org/GNOME/gtk/-/commit/51b04c5007f89142ed5a1ab240c03d5800b86b3d
A quick fix uses monitor's model attribute to do the match instead of geometry, as for now, the geometry.x and geometry.y will always be 0,0 regardless the real monitor position.